Greptile Summary

This PR moves project management from a process-local MemoryStore into a proper service layer at backend/internal/service/project, aligning it with the session service structure introduced in #67. It introduces domain.ProjectRecord as the shared storage row shape, exposes explicit persistence methods on the sqlite store, trims the project HTTP surface to the four implemented routes, and regenerates openapi.yaml to cover both project and session endpoints.

• service/project.Service correctly guards archived rows in Get and Add using ArchivedAt.IsZero(), and the SQL source for ArchiveProject was fixed with AND archived_at IS NULL to prevent double-delete returning 200 — but sqlc generate was not re-run for that query, so the compiled archiveProject constant in gen/projects.sql.go still lacks the guard (see inline comment).
• FindProjectByPath was correctly re-generated with its AND archived_at IS NULL guard, and the UpsertProject ON CONFLICT path correctly clears archived_at to NULL when re-registering a previously removed project.
• Controller, daemon wiring, and test suite are all updated to depend on the new service interface rather than the old in-memory manager.

Confidence Score: 4/5

Safe to merge after regenerating the sqlc output — the SQL source is correct but the compiled constant for ArchiveProject is one generation behind.

The service logic, archived-row filtering, and re-add-after-remove flow are all correct. The one concrete defect is the archiveProject constant in gen/projects.sql.go: the SQL source was patched with AND archived_at IS NULL but sqlc generate was not re-run for that query, so a second DELETE on the same project still returns 200 OK at runtime. Everything else — the domain type, store interface, controller wiring, and test coverage — looks sound.

backend/internal/storage/sqlite/gen/projects.sql.go — the archiveProject constant needs to be regenerated to pick up the AND archived_at IS NULL guard that is already present in projects.sql.

Important Files Changed

Sequence Diagram

sequenceDiagram
    participant C as HTTP Controller
    participant S as service/project.Service
    participant ST as sqlite Store
    participant DB as SQLite DB

    Note over C,DB: Add project
    C->>S: Add(ctx, AddInput)
    S->>ST: FindProjectByPath(path)
    ST->>DB: "SELECT WHERE path=? AND archived_at IS NULL"
    DB-->>ST: ErrNoRows
    ST-->>S: "ok=false"
    S->>ST: GetProject(id)
    ST->>DB: "SELECT WHERE id=?"
    DB-->>ST: row, ok
    Note over S: if ok and ArchivedAt.IsZero() and path differs, return ID conflict
    S->>ST: UpsertProject(record with zero ArchivedAt)
    ST->>DB: "INSERT ON CONFLICT DO UPDATE SET archived_at=NULL"
    S-->>C: "Project{}"

    Note over C,DB: Remove project
    C->>S: Remove(ctx, id)
    S->>ST: ArchiveProject(id, now)
    ST->>DB: "UPDATE SET archived_at=? WHERE id=?"
    Note over DB: Missing AND archived_at IS NULL in gen file
    DB-->>ST: "rowsAffected=1 even if already archived"
    ST-->>S: "ok=true"
    S-->>C: RemoveResult 200 OK

    Note over C,DB: Get project
    C->>S: Get(ctx, id)
    S->>ST: GetProject(id)
    ST->>DB: "SELECT WHERE id=?"
    DB-->>ST: row, ok
    Note over S: if not ok or not ArchivedAt.IsZero() return PROJECT_NOT_FOUND
    S-->>C: "GetResult{Status:ok, Project}"

_{Reviews (8): Last reviewed commit: "refactor: move pr manager into service l..." | Re-trigger Greptile}

go test ./... is currently failing on PR 68 in backend/internal/httpd/apispec/specgen: the drift test says the embedded backend/internal/httpd/apispec/openapi.yaml is stale compared with fresh specgen.Build() output. I confirmed that running go generate ./... from the backend/ directory regenerates the spec and makes go test ./internal/httpd/apispec/specgen pass, so the fix is to regenerate and commit openapi.yaml. Since this surfaced on a Windows checkout, it may also be worth adding a .gitattributes rule such as backend/internal/httpd/apispec/openapi.yaml text eol=lf, or normalizing line endings in the test, so the byte-for-byte drift check does not fail across Windows/Linux checkouts